Tooling system

ABSTRACT

A tooling system may comprise a tool scanner, a tool database, and a user interface device. The tool scanner may be configured to scan a tool identifier on a tool. The tool database may have tool information associated with the tool identifier. The user interface device may be in communication with the tool scanner and the tool database. The user interface device may receive tool information from the tool database in response to the scan by the tool scanner, concurrently display a tool issue description and a tool issue image from the tool information of the tool database, receive a tool area selection with respect to the tool issue image, and provide access to a tool issue history from the tool database in response to the tool area selection.

RELATED APPLICATIONS

This application is a Continuation-In-Part Application of U.S. patentapplication Ser. No. 14/266,423 filed Apr. 30, 2014, now U.S. Pat. No.9,292,811, issued Mar. 22, 2016, which is a Continuation-In-PartApplication of U.S. patent application Ser. No. 13/690,097 filed Nov.30, 2012, which is based on and claims priority to U.S. ProvisionalPatent Application No. 61/605,366 filed Mar. 1, 2012, all of which areincorporated by reference in their entirety.

FIELD OF TECHNOLOGY

The present disclosure relates to systems using tool identifiersincluding machine readable labels on tools. More specifically, itincludes a system that utilizes machine readable labels, such asbarcodes, that are integrated with, or affixed to, molds and dies, orother assets used in the manufacturing of product, thereby permitting auser to access critical tool information, report issues, set alerts, andtrack tooling activity related to that specific tool.

BACKGROUND

Tools such as molds and dies are used to manufacture products such asplastic parts, e.g., those formed by injection molding. In order to usea given tool properly, the operator must possess certain informationabout the tool. Such critical information might include the toolmanufacturer, process parameters, construction drawings, dimensionalinformation and useful life of the tool. Often times these tools aresent from one plant to another, but critical information related to thetool is not provided, is incomplete, or is lost. This can be veryproblematic in a manufacturing setting where multiple tools are used, asit is not necessarily easy to distinguish one tool from another by mereinspection. It can be time consuming to perform the investigative workrequired to determine the identity of a specific tool, or even wastefulor dangerous if a misidentified tool is inadvertently used.

There is a need for a system that allows a tool manufacturer to providecritical information such as tool information that is related to thetool itself. It is desirable that the object with this information doesnot affect the performance of the tool, and that it is easily readableby the tool operator. It is also desirable that this information bedynamic insofar as it can be updated by the tool operator or agentthereof. Accordingly, the present disclosure provides improvements inthis area.

BRIEF DESCRIPTION OF THE DRAWINGS

While the claims are not limited to a specific illustration, anappreciation of the various aspects is best gained through a discussionof various examples thereof. Referring now to the drawings, exemplaryillustrations are shown in detail. Although the drawings represent theillustrations, the drawings are not necessarily to scale and certainfeatures may be exaggerated to better illustrate and explain aninnovative aspect of an example. Further, the exemplary illustrationsdescribed herein are not intended to be exhaustive or otherwise limitingor restricted to the precise form and configuration shown in thedrawings and disclosed in the following detailed description. Exemplaryillustrations are described in detail by referring to the drawings asfollows:

FIG. 1 represents a tool management system with a quick response(QR)-type barcode affixed to a tool, with various embodiments of aQR-type barcode being depicted in the exploded views of FIGS. 1A-1D;

FIG. 2 depicts a tool system having a UPC-type barcode inscribeddirectly on a tool, with the barcode shown in an exploded view in FIG.2A;

FIG. 3 schematically represents some components of a tool managementsystem;

FIG. 4A represents a user interface for inputting information;

FIG. 4B represents a plaque on a tool; and

FIG. 4C represents a user interface for querying information;

FIG. 5 illustrates a schematic diagram of a system and method ofreporting metrics of the history of a tool;

FIG. 6 illustrates a schematic diagram of a system and method ofgenerating a Preventative Maintenance (PM) alert system;

FIG. 7 illustrates a schematic diagram of a system and method oftracking the lifecycle count of a tool for use in a PM alert system;

FIG. 8 illustrates a schematic diagram of a system and method ofauto-populating a tool database wherein tool data gathered during atrial run is recorded. This data, including but not limited to, setup,calibration, and process data, is auto-populated into the host machinein order to attempt to match the performance the tool had during thetrial;

FIG. 9 illustrates a schematic diagram of a system and method oftracking tools and updating a database using a global positioning system(GPS) as part of a cellular phone or using cellular triangulation by wayof a cellular network;

FIG. 10 illustrates another user interface of a tooling system, e.g.,for automated access, reporting, and distribution of tool informationand issues; and

FIG. 11 illustrates another user interface of a tooling system, e.g.,for automated displaying and reporting of tool information and issues.

DETAILED DESCRIPTION

A system may be configured to utilize tool identifiers such as machinereadable labels affixed to tools for managing information related tothose tools uses components such as barcodes, processors, and barcodereaders. A specially created and unique barcode is created when a usercreates a profile for a specific tool. This barcode is affixed to a toolin such a manner that the barcode does not interfere with use of thetool. The barcode preferably has additional human-readable printingwhich directs a user to a website. By accessing the website and scanningthe barcode on the specific tool, a user is able to access pertinentinformation such as tool information related to that tool. Optionally,authorized users may also be able to update information related to thattool. In this manner, manuals, specifications and so forth that areassociated with the tool can't be lost or misplaced. Examples ofpertinent information include specifications, recalls, current orrecommended hours of usage, liens and so forth.

A method of reporting metrics of the history of a tool that includes,but is not limited to, the ability to create, report, store, andcommunicate tool information such as machine tool details, parameters,usage, issues, maintenance actions, and or problems. Also, a method ofgenerating a Preventative Maintenance (PM) Alert report which includes,but is not limited to, calendar data on when recommended maintenance forthe tool is due or near due, generates periodic reminders, and can listPM steps to take. Additionally, a method of tracking the lifecycle countof a tool for use in a PM alert system. Also, a method ofauto-populating a tool database. Finally, a method of tracking toollocations and updating tool metrics utilizing a GPS- and camera-enabledcellular phone.

Referring to FIG. 1, an information management system 10 may include,but is not limited to, a barcode 12, a barcode plate 13, a tool 15, aplaque 20, a barcode reader 25, a processor 30, and an output display35. As used herein, a “tool” is a device, machine or apparatus that isportable and used in the manufacture of goods and products. Examples of“tools” include tool and dies, molds, controllers, machines, fixtures,hot runner systems, and secondary equipment.

As shown in FIG. 1A, barcode 12 maybe situated on barcode plate 13,which is affixed to plaque 20, with plaque 20 attached to a tool 15. Inthis manner barcode plate 13 is not directly attached to tool 15, asplaque 20 is sandwiched between.

In this embodiment it is possible that the barcode plate 13 substrate isaluminum, steel, with barcode 12 markings effectuated by printing,etching, laser imprinting, and inscribing. It is possible that surfaceof barcode plate 13 has approximate dimensions of 2.75 inches by 3.5inches to 2.75 inches by 5 inches. Thickness of barcode plate 13 may beapproximately 1 millimeter to 3 millimeters.

A plaque 20 has a substrate made of metal, such as but not limited toaluminum and/or steel, with surface dimensions of approximately 2.75″ by3.5″ to 9″ by 11″. Thickness of plaque 20 is approximately 1 mm to 3 mm.It is desirable that plaque 20 is slightly larger than barcode plate 13.

Attachment of the various components, including barcode plate 13 andplaque 20 to tool 15, should be substantially permanent, yet notinterfere with the operation of the tool. For example, in the case of atool and die, barcode plate 13 and plaque 20 should be attached to thefixed (non-moving) portion of tool 15. Attachment of barcode plate 13and plaque 20 to tool 15 can be effectuated by a variety of methodsincluding, but not limited to, adhesion, welding, and bolting.

In an alternative embodiment, shown in FIG. 1B, barcode 12 is situatedon barcode plate 13, which is attached directly to tool 15. In otherwords there is no plaque 20. In yet another embodiment, shown in FIG.1C, plaque 20 is inscribed with barcode 12, which is attached to tool15. In other words, there is no barcode plate 13. In another exemplaryembodiment, FIG. 1D presents a tool 15 having a barcode-like device 12affixed or otherwise secured to a surface of the tool 15. As will beappreciated, the barcode 12 may attached to the tool 15 directly orindirectly by a variety of systems.

Turning now to FIG. 2, it is also within the scope of this disclosure tosituate the barcode directly onto tool 15. In this embodiment there isno plaque 20 and no barcode plate 13. Such inscription can be byetching, engraving, laser engraving or the like.

A variety of barcode types or symbologies can be used, for examplematrix (2D) such as QR, or linear (1D) such as UPC, as shown in FIGS. 1and 2 respectively.

An overview of the tool management system 10 is schematically depictedin FIG. 3, wherein system 10 includes tool 15 having a tool identifiersuch as barcode 12; a barcode reader 25; an output display 35; and aprocessor 30. A user wanting critical information such as toolinformation related to tool 15 would use barcode reader 25 to scanbarcode 12. Reader 25 can be a variety of devices including a designatedscanner, such as a fixed light and photosensor device, or a so called“smart phone” with the appropriate application such as “Scan” or“mbarcode”, as shown. Reader 25 transmits a query to processor 30 forinformation linked to barcode 12, and processor 30 transmits criticalinformation such as tool information to reader 25, for user's viewingthrough output display 35. Output display 35 may be included withbarcode reader 25, for example a smart phone. This embodiment isdepicted in FIG. 3. Processor 30 may include any or a combination of aweb server, cloud computing server, tablets, smartphones, wirelessdevices, or other data processing and/or storage device.

An embodiment and method of using the system 10 is depicted in greaterdetail in FIGS. 4A-4C. FIG. 4A is a sample user interface that a userwould enter information into so as to register a tool 15 which has notyet been registered. Other relevant information that could be useful inregistering a tool includes tool information such as the date ofmanufacture, warranty information, authenticity of tool, tool set up,design information, and tool maintenance. Upon successfully enteringinformation into the system, as set forth in FIG. 4A, a user receives,preferably by mail, a plaque including the associated barcode. This isdepicted in FIG. 4B. The plaque is preferably printed or otherwisemarked so as to direct future tool users to a website to query or updateinformation linked to the tool. A subsequent tool user could obtain orupdate tool information about the tool 15 by scanning the barcode andaccessing the website which is identified on the plaque of FIG. 4B,which would take them to a user interface such as that set forth in FIG.4C. From there the user could obtain or update a variety of information.

One advantage of system 10 is that critical information such as toolinformation related to tool 15 can be updated as necessary, includingcorrections to specifications, additional safety warnings, messages thata tool is subject to a lien, or that the useful life of a tool is comingto an end. Such an update would be entered by way of the user interfaceinto processor 30, so subsequent barcode reader 25 queries would yieldthis additional information on output display 35. It should be notedthat a variety of information can be associated with each tool, andshould not be construed to be limited to that which is specifically setforth herein. FIG. 5 illustrates a schematic diagram and a method forreporting metrics of the history of a tool in order to create, report,store, and communicate tool information such as machine tool details,parameters, usage, issues, maintenance actions, and/or problems. TheIssue Reporting System 100 and method is comprised of a tool operator102, a machine tool 104, an optical or RF machine-readablerepresentation of data 106 that is fixably attached to the machine tool104, a scanner device 108, an input/output (I/O) device 110, a computer112, machine tool data 114, a tool database 116, an issue report 118, analert report 120, and a remote terminal 122.

The machine tool 104 is described as a device for shaping or machiningmetal or other rigid materials, usually by cutting, boring, grinding,shearing, or other forms of deformation. Machine tools are typicallypowered other than by human muscle (e.g., electrically, hydraulically,or via line shaft) and are used to make manufactured parts in variousways that include cutting or certain other kinds of deformation.

The Optical or RF machine-readable representation of data 114 (which isrelating to the object to which it is attached) is commonly referred toas “Automatic Identification and Data Capture” (AIDC). AIDC refers tothe methods of automatically identifying objects, collecting data aboutthem, and entering that data directly into computer systems (i.e.without human involvement). AIDC may include bar codes, Radio FrequencyIdentification (RFID), biometrics, magnetic stripes, Optical CharacterRecognition (OCR), smart cards, and voice recognition. AIDC is alsocommonly referred to as “Automatic Identification,” “Auto-ID,” and“Automatic Data Capture.” AIDC also refers to the methods of recognizingobjects, getting information about them, and entering that data orfeeding it directly into computer systems without any human involvement.AIDC capture technologies include optical/RF code devices, RFID,barcodes, OCR, magnetic stripes, smart cards and biometrics (like irisand facial recognition system).

The scanner 108 may include an optical and or electronic device forreading AIDC. In one example, the scanner 108 consists of a lightsource, a lens and a light sensor translating optical impulses intoelectrical signals. Other embodiments of the scanner 108 include theability to transmit and receive data from a RFID tag using wirelesstechnology. Additionally, nearly all readers contain decoder circuitryanalyzing the AIDC's image data provided by the sensor and sending theAIDC's content to the scanner's 108 output port.

The I/O device 110 may include a device with a wired or wirelessconnection with a computing device (such as computer 112) and that isused by a person (or other system) to communicate with the computingdevice. An I/O device 110 is the communication device between aninformation processing system (such as computer 112) and the outsideworld, possibly a human or another information processing system.

Computing systems and/or devices, such as the computer 112, may employany of a number of computer operating systems, including, but notlimited to, versions and/or varieties of the Microsoft Windows®operating system, the Unix operating system (e.g., the Solaris®operating system distributed by Oracle Corporation of Redwood Shores,Calif.), the AIX UNIX operating system distributed by InternationalBusiness Machines of Armonk, N.Y., the Linux operating system, the MacOS X and iOS operating systems distributed by Apple Inc. of Cupertino,Calif., the BlackBerry OS distributed by Research In Motion of Waterloo,Canada, and the Android operating system developed by the Open HandsetAlliance. Examples of computing devices include, without limitation, amobile device, a cellular phone, a smart-phone, a super-phone, a tabletcomputer, a next generation portable device, a computer workstation, aserver, a desktop, notebook, laptop, or handheld computer, or some othercomputing system and/or device. Computing devices, such as the computer112, may include computer-executable instructions such as theinstructions of the tool database 116 where the instructions may beexecutable by one or more computing devices such as those listed above.Computer-executable instructions may be compiled or interpreted fromcomputer programs created using a variety of programming languagesand/or technologies, including, without limitation, and either alone orin combination, Java™, C, C++, C#, Objective C, Visual Basic, JavaScript, Perl, etc. A processor (e.g., a microprocessor) receivesinstructions, e.g., from a memory, a computer-readable medium, etc., andexecutes these instructions, thereby performing one or more processes,including one or more of the processes described herein. Suchinstructions and other data may be stored and transmitted using avariety of computer-readable media.

A computer-readable medium (also referred to as a processor-readablemedium) includes any non-transitory (e.g., tangible) medium thatparticipates in providing data (e.g., instructions) that may be read bya computer (e.g., by a processor of a computer). Such a medium may takemany forms, including, but not limited to, non-volatile media andvolatile media. Non-volatile media may include, for example, optical ormagnetic disks and other persistent memory. Volatile media may include,for example, dynamic random access memory (DRAM), which typicallyconstitutes a main memory. Such instructions may be transmitted by oneor more transmission media, including coaxial cables, copper wire andfiber optics, including the wires that comprise a system bus coupled toa processor of a computer. Common forms of computer-readable mediainclude, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, any other magnetic medium, a CD-ROM, DVD, any otheroptical medium, punch cards, paper tape, any other physical medium withpatterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any othermemory chip or cartridge, or any other medium from which a computer canread.

Tool database 116, data repositories, or other data stores describedherein may include various kinds of mechanisms for storing, accessing,and retrieving various kinds of data, including a hierarchical database,a set of files in a file system, an application database in aproprietary format, a relational database management system (RDBMS),etc. Each such data store is included within a computing deviceemploying a computer operating system such as one of those mentionedabove, and are accessed via a network in any one or more of a variety ofmanners. A file system may be accessible from a computer operatingsystem, and may include files stored in various formats. An RDBMSemploys the Structured Query Language (SQL) in addition to a languagefor creating, storing, editing, and executing stored procedures, such asthe PL/SQL language mentioned above.

In some examples, system elements may be implemented ascomputer-readable instructions (e.g., a program such as software) on oneor more computing devices (e.g., servers, personal computers, etc.),stored on computer readable media associated therewith (e.g., disks,memories, etc.). A computer program product may comprise suchinstructions stored on computer readable media for carrying out theoperations and functions described herein.

An exemplary tooling system may include a user interface device having adisplay, a hardware processor, memory, and a transceiver. For example,the device may be in communication with a tool scanner (e.g., as part ofthe device or in wired or wireless connection therewith) and a tooldatabase (e.g., by way of a network). The device may receive (e.g., byway of the transceiver) tool information from the tool scanner and tooldatabase, generate (e.g., by way of the processor) a comparison betweenthe tool information from at least two of memory of the user interface,tool scanner, and tool database, store (e.g. by way of memory) the toolinformation and the comparison, transfer (e.g., by way of thetransceiver) the tool information and the comparison to the toolscanner, tool database, or another device, and display the toolinformation and comparison on the interface device.

Continuing with FIG. 5, the issue report 118 contains, but is notlimited to, tool information such as tool issues including a summary orlist of any problems the operator 102 notices such as a high rejectionrate, cracks, chips, or other physical defects visible to the operator102, out-of-tolerance issues witnessed by the operator 102, etc. In thismanner, operator 102 can both submit new data to the database 116 andretrieve and access the latest information associated with the tool 104.The issue report 118 gives both the operator 102 and a factory ownerrapid access to tool information such as emerging tool parameters innear real-time, allowing both the owner and operator 102 to respondquickly to degraded or damaged tools 104 before that tool 104 is used inproduction. This gives an advantage in both time and money for theowner/operators.

FIG. 5 also contains an alert report 120 which may include, but is notlimited to, details on the tool 104 such as replacement notifications,preventative maintenance (PM) reminders, whether the tool 104 is subjectto contract/license/lien restrictions, or whether tool 104 has been thesubject of special instructions or notices issued from the tool'smanufacturer. The alert report 120 can be a printed report and or anelectronic data message 206. Generating an alert report 120 in nearreal-time gives a business advantage to the owner of a factory as recallnotices can be delivered quickly directly to the operator 102.Additional benefits include quickly identifying defective tools 102 andisolating said tools before they are used in production. Furthermore,reminders for renewing liens and licenses can be quickly sent out tointerested parties.

The method of reporting metrics is comprised of the following steps asshown in FIG. 5. It will be appreciated that more or fewer steps may beutilized.

Step 1. The operator 102 scans the optical/RF code device 106 on thetool 104 using a scanner 108.

Step 2. The data 114, e.g., tool information, is sent to the computer112 where the data 114 is saved to the database 116. The computer 112 iseither located in close physical association with the scanner 108 or isin electronic communication with the scanner 108 via a computer wired orwireless network or cabling system. The database stores and analyzesdata 114 entered into the system; the data 114 may be, but is notlimited to, tool information such as the tool's serial number or otherunique identifying number associated with only that tool, the tool'sdate of manufacture, warranty information, authenticity of the tool,tool set-up information, lien information on the tool, contract/licenseinformation, design information, special use instructions, toolmaintenance instructions, history of the tool, etc. It should be notedthat this list of data fields are merely examples and it is notpresented in this application as a limiting set of data fields.

Step 3. The computer 112 then retrieves pertinent data 114 from thedatabase 116 and sends it to the scanner 108 or I/O device 110 where thedata can be reviewed by the operator 102.

Step 4. The operator can also generate an issue report 118 by enteringinformation (e.g., tool information) into the scanner 108 or I/O device110. The issue report 118 may contain, but is not limited to, all of theinformation the operator 102 provides and may be augmented by additionalinformation gathered from the database 116. The information in the issuereport 118 thus may contain, but is not limited to, tool informationsuch as the tool's serial number or other unique identifying numberassociated with only that tool, the tool's date of manufacture, warrantyinformation, authenticity of the tool, tool set-up information, lieninformation on the tool, contract/license information, designinformation, special use instructions, tool maintenance instructions,history of the tool, etc. It should be noted that this list of datafields are merely examples and it is not presented in this applicationas a limiting set of data fields. The issue report may be sent to apre-determined group of remote computer terminals 122 or emailrecipients, as desired.

Step 5. With the latest data entered into the database 116, the computer112 can run algorithms and generate an alert report 120. The alertreport 120 may contain, but is not limited to, tool informationregarding the tool's 104 status, an issue description field, fields totrack cost and hours spent on the issue, who reported the issue, wherethe issue was reported from, date and time the issue was generated, afield to attach photographs, diagrams, guidelines, files, etc., fieldsto record materials or parts used on the issue, an area to include stepstaken to resolve the issue, a Q&A section for communicating betweenparties, whether the tool needs maintenance, whether an out-of-warrantycondition exists, any contract/license/lien information, specificalignment parameters associated with that tool 104, instructions on howto operate and use that tool 104, whether the tool 104 needs to be takenout of service, whether the tool is subject to a recall notice, etc.

Step 6. This alert report 120 is sent back to the operator 102 and maytake the form of an electronic message 206 sent to the scanner 108 orI/O device 110, an electronic message 206 to a computer, or a printoutfrom a printer. The preferred embodiment is for the operator 102 toreceive the alert report 120 on the I/O device 110 or on the scanner 108as soon as it is generated.

Step 7. Finally, the alert report 120 may be sent to a pre-determinedgroup of remote computer terminals 122 or email recipients, as desired.

In an alternative embodiment, the I/O device 110 shown in FIG. 5 couldbe an optical/RF scanner, a barcode scanner with a screen, or either ofthese devices with a graphical user interface. The operator 102 mayenter the tool data 114 using a graphical user interface device such asa remote terminal 122 near the tool 104 location.

FIG. 6 illustrates an alternative system 200 and method of generating aPreventative Maintenance (PM) Alert system 200. System 200 is similar tosystem 100 in that the operator 102 scans the tool 104 and enters thedata 114 into the database 116, but here system 200 performs a differentfunction with the scanned data 114 that makes its way into the database116. System 200 performs additional functions by collecting andanalyzing usage information on the tool 104. The system 200 thenprocesses the information to see if PM is recommended and generates a PMschedule report 202. In FIG. 6, where possible, like references andnumerals are used for simplicity purposes.

The system 200 is comprised of a PM schedule report 202 and alert report120. The system 200 is used to generate a PM schedule report 202 for thetool 104 being accessed. The operator 102 begins the process by scanningthe tool's 102 optical/RF code device 106 using a scanner 108 to enterthe data 114 into the database 116 via the computer 112. Once the data114 is in the database 116, it is used to augment the library of datagathered on that specific tool 104. It will be appreciated that more orfewer steps may be utilized.

PM schedule report 202 includes, but is not limited to, calendar data onwhen recommended maintenance for the tool 104 is due or near due,generates periodic reminders via an alert report 120 to notify personnelof upcoming deadlines for PM procedures, and can list the specific stepsrequired of the operator 102 to perform preventative maintenance on thetool 104.

The tool database 116 may output PM parameters 204. Based on a set ofpre-arranged markers, guideposts, or limit parameters, the database 116may generate an alert report 120. The alert report 120 is sent back tothe operator 102 with a message 206 that provides instructions to clean,maintain, or remove the tool for service and cleaning. Furthermore, thealert report 120 can be sent to a pre-determined group of remotecomputer terminals 122 or email recipients 110, as desired.

FIG. 7 illustrates an alternative embodiment where a system 300 andmethod of tracking the lifecycle of a tool 104 is disclosed. System 300is similar to system 100 in that the operator 102 scans the tool 104 andenters the data 114 into the database 116, except system 300 performs adifferent function with the scanned data 114 that makes its way into thedatabase 116. System 300 performs a preventative maintenance cycle countfunction and retains this information as the tool 104 is moved from onemachine 304 to another machine 306. The system 300 then processes theinformation to see if PM is recommended and generates an alert report120. In FIG. 7, where possible, like references and numerals are usedfor simplicity purposes. By having the operator 102 scan the tool 104every time it is used, a usage history is generated which assists intracking the tool lifetime and history. By accessing the usage historyof a tool 104, the owner and operator 102 of a tool 104 may track thelifetime, the PM history, any faults or alerts, and specific setupinstructions for the tool 104 regardless of which machine 304, 306 isused to host the tool 104.

The PM Alert (Cycle Counter) system 300 can be performed by the user byfollowing these steps below. In FIG. 7, where possible, like referencesand numerals are used. It will be appreciated that more or fewer stepsmay be utilized. Components of system 300 include a PM schedule report302, a machine A 304, a machine B 306, both machines 304, 306 eitherlocated physically close to one another or physically isolated form oneanother, and a count data process 308.

Step 1. The tool 104 may be removed from the machine 304 and relocatedto another machine 306. This feature allows each tool 104 to be incommunicative association with its customized tool metrics databaserecord regardless of the physical location of the tool 104 or of thecomputer 112 managing the database 116. This gives the operator 102advantages when managing large numbers of tools 112, tools 104 used inphysically different machines 304, 306 located in the same facility, andtools 104 used in machines 304, 306 located in different facilities andseparated by large distances.

Step 2. The operator 102 installs the tool 104 into a new machine 306and scans the optical/RF code device 106 using the scanner 108.

Step 3. The data 114 is sent to the database 116 which is updated andwhere the tool 104 metrics are retrieved. The tool 104 metrics mayinclude, but are not limited to, tool information such as technical andbusiness metrics such as contract information, license details, lieninformation, expiration data, warranty data, special instructions,recall data, or other information deemed important by the toolmanufacturer or the tool user.

Step 4. The data 114 is also sent back to the scanner 108 or I/O device110 for immediate use by the operator 102.

Step 5. The operator 102 sets metric parameters to monitor tool 104 lifesuch as per use, per hour, per day, etc. This data 114 is sent to thedatabase 116 for storage and analysis.

Step 6. The tool 104 is operated and or runs cycles, wherein at the endof each cycle the operator 102 scans the optical/RF code device 106 toupdate the database 116 again, and periodically throughout the workshift.

Step 7. The computer 112 monitors the cycle count for that specific tool104 and once a pre-set number of cycles are reached, generates anautomated alert report 120 which is sent back to the operator 102 andvia email in a pre-determined list of preferred contacts.

Step 8. The PM schedule report 302 may include, but is not limited to amessage 206 that provides instructions to check the tool, check theparts being produced, check the fixture & gauges being used, check the“end of arm tooling”, or check other secondary equipment associated withthe tool or machine being used.

FIG. 8 illustrates an alternative embodiment showing that system 400differs from system 100 as shown in FIG. 5 in that the scanning isperformed automatically verses having an operator 102 manually scan thetool 104. System 400 discloses a method of auto-populating the database116. It will be appreciated that more or fewer steps may be utilized.System 400 includes machine A 304 and machine B 306, which may bemachines that use tools 104 but are physically isolated from oneanother. In FIG. 8, where possible, like references and numerals areused for simplicity purposes.

System 400, as seen in FIG. 8, runs an “Auto-populate” process where thedatabase 116 stores and analyzes data 114 associated with a specifictool 104. This data 114 may include, but is not limited to, toolinformation such as technical and business metrics such as contractinformation, license details, lien information, expiration data,warranty data, special instructions, recall data, or other informationdeemed important by the tool manufacturer or the tool user. In thismanner, the operator 102 has ready the very latest usage, operation,ownership, and safety data on that tool 104 every time the tool 104 isused.

The details of how system 400 may operate could include the followingprocess. The tool 104 is automatically scanned by the host machine 304where the machine 304 is in electronic communication with the computer112 and database 116. Every time the tool 104 is used, inserted, orremoved, that data 114 is forwarded for analysis. When analyzed withother individual tool metrics collected over time, the tool manufacturercan run statistical quality control analysis or “Six Sigma” analysis forthe entire tool production run. In this manner, the tool manufacturercan monitor customer preferences, estimate tool family life, see trendsin tool 104 usage, detect possible quality control issues, and othervaluable business details. This analysis can help estimate present andfuture business needs as well as detect quality problems quickly andwithout needlessly contacting the customer for periodic updates.

As seen in FIG. 8, a further embodiment can be envisioned where the data114 collected by the system 400 may be used by the tool manufacturer forbusiness purposes. This data 114, collected from the individual tooloperators 102, is collected and analyzed by the tool manufacturer togarner metrics on the entire tool family, defined as the totalproduction of individual tools 104 in use throughout the industry. Thetool manufacturer can monitor when a tool 104 is first used, tool usage,tool 104 replacement rates, and tool 104 lifetime rates.

As seen in FIG. 9, a further embodiment can be envisioned where system500 is similar to system 100 in that the operator 102 scans a tool 104and enters the data 114 into a database 116. System 500 contains, but isnot limited to, a GPS- and camera-enabled cellular phone 502 andutilizes a GPS-enabled cellular phone cellular network 504. A toollocation may be generated from a GPS as part of the cellular phone 502or from cellular triangulation by way of cellular network 504. In FIG.9, where possible, like references and numerals are used for simplicitypurposes.

However, in this embodiment, the differences from system 100 as shown inFIG. 5 and system 500 shown in FIG. 9, the scanning device is a cellularphone with GPS and camera capability 502 that has the ability to take aphotograph or scan the tool 104 and enter the data 114 into the database116. This embodiment gives the owner/operator 102 the advantages ofusing a small portable scanner in the form of the cellular phone 502. Anadditional advantage is this embodiment gives the tool owner/operator102 the ability to record and track the tool's 104 location every timethe tool is scanned. In this manner, a permanent record of the tool'swhereabouts are made and stored in the database 116.

FIG. 10 illustrates tooling system 600 including a user interface of adevice, e.g., for accessing, reporting, and distributing toolinformation including tool issues. System 600 may include boxes,windows, areas, or buttons that are concurrently or sequentiallydisplayed for inputting, displaying, and/or accessing one or more ofproject identification number 602, view project 604, report issue 606,send GPS information 608, message 610, and log in 612. Projectidentification number 602 may be configured to receive tool informationsuch as a project identification number regarding a tool. View project604 may be configured to display tool information. Report issue 606 maybe configured to receive tool issues regarding the tool. Send GPSinformation 608 may be configured to send a tool location based on aGPS. Message 610 may be configured to send a message including toolinformation. Log in 612 may be configured to log in a user for inputtingand viewing tool information.

FIG. 11 illustrates tooling system 700 including a user interface of adevice, e.g., for e.g., for displaying and reporting tool informationincluding tool issues. The user interface of the system 700, in a firstdisplay area, may concurrently or sequentially display boxes, windows,areas, or buttons for inputting, displaying, and/or accessing toolinformation including one or more of toolmaker project number 702 for aproject associated with a tool, production tool number 704 with a toolnumber of the tool, issue reported by 706 with a name of the personreporting the tool issue, company name 708 with the company associatedwith the person reporting the tool issue, plant location 710 including atool location by an area, room, or floor of a facility, and issuedescription 712 with details of the tool issue,

In the same or a second display area, the user interface of the system700 may concurrently or sequentially display boxes, windows, areas, orbuttons for inputting, displaying, and/or accessing tool informationincluding one or more of repair hours 713 with an estimated or incurrednumber of hours to repair the tool issue, minimum 713 with a minimum,estimated, or incurred services cost for the tool issue, materials cost716 with an estimated or incurred cost for the tool issue, projectedcost 718 with the total or projected costs of the tool issue, createapproval form 720 to create a customer approval form or checklist forapproving repair of the tool issue, create or view checklist 721 foritemizing phases or components of repairing the tool, and electronicsign off 722 for authorizing repair of the tool.

Furthermore, in the same or a third display area, the user interface ofthe system 700 may concurrently or sequentially display boxes, windows,areas, or buttons for inputting, displaying, and/or accessing toolinformation including one or more of tool setup 723 including tool setupinformation and instructions, tool design 724 including tool designinformation and instructions, tool maintenance 725 including toolmaintenance information and instructions, manufacture info 726 includingmanufacture date, manufacture location, and manufacturer name, warrantyinfo 727 including warranty status, warranty details, total warrantyterm, and remaining warranty term, authenticity info 728 includingauthentication information for the tool, lien information 729 includingany lien placement, lean release, loan, ownership, and paymentinformation, histories, or terms for the tool, e.g., from a UniformCommercial Code (UCC) database, and enable/disable tool 730 allowing theuser to selectively enable and disable the tool in response to any toolinformation, e.g., failure to pay for the tool according to paymentterms.

The user interface of the system 700, in the same or a forth displayarea or section, may also concurrently or sequentially display boxes,windows, areas, or buttons for inputting, displaying, and/or accessingtool information including one or more of view 731 to view toolinformation and images, convert 732 to convert the file format of thetool information and images to another file format selected by the user,size 733 including the file size of the tool information and images,status 734 including a file conversion status, add files 735 includingany electronic or scanned documents related to the tool, attach photo736 including an image of the tool, and add notes 738 including anynotes and comments regarding the tool issue near or directly on the toolimage.

In the same or a fifth display area or section, the user interface ofthe system 700 may further concurrently or sequentially display boxes,windows, areas, or buttons for inputting, displaying, and/or accessingtool information including one or more of contract list 740 includingpredefined contacts and email addresses, add email 742 to add predefinedcontacts and email addresses, and remove email 744 to remove predefinedcontacts and email addresses.

In addition, the user interface of the system 700, in the same or asixth display area, may further concurrently or sequentially displayboxes, windows, areas, or buttons for inputting, displaying, and/oraccessing tool information including one or more of tool image 746 ofthe tool, current 748 to display the latest or a current scan or imageof the exterior and interior surfaces of the tool, scan new 750 tocapture or import a new scan or image of the tool, add issue 754 toassociate tool issues with the tool image or scan associated with one ormore tool issues, and issue history 756 to display or access a listingof tool issues. Add issue 754 may be configured to select one or both ofthe first and second sides 758, 760 of the tool, e.g., the cavity andcore sides of a mold. Tool image 746 may include sections 762 a, 762 b,762 c, 762 d of the first side 758 and sections 764 a, 764 b, 764 c, 764d of the second side 760, e.g., for making a tool area selection withrespect to the tool issue image and association with one or more toolissues.

System 700 may include a tooling system. System 700 may include a toolscanner 108 configured to read or scan a tool 15, a tool database 116having tool information associated with a tool identifier 12, and a userinterface device 35 in communication with the tool scanner 108 and thetool database 116. The user interface device 35 may receive toolinformation from the tool database 116 in response to the scan by thetool scanner 108, concurrently display a tool issue description 712 anda tool issue image 746 from the tool information of the tool database116, receive a tool area selection 762, 764 with respect to the toolissue image 746, and provide access to a tool issue history from thetool database 116 in response to the tool area selection 762, 764. Theuser interface device 35 may further concurrently display at least one,two or three types of data 114 including tool information such as toolset-up information, design information, maintenance instructions, toolcondition, manufacture date, warranty information, and authenticityinformation from the tool information of the tool database. The userinterface device may further concurrently display additional data 114such as a tool location from at least one of a global positioning system(GPS) and cellular triangulation. The user interface device may furthersend data 114 such as tool information to a predetermined list ofcontacts associated with the tool 15.

Methods of using the system 700 are also contemplated. A method mayinclude receiving data 114 such as tool information from the tooldatabase 116 in response to the scan by the tool scanner 108. A methodmay further include concurrently displaying a tool issue description 712and a tool image 746 (e.g., with a tool issue) from the data 114including tool information of the tool database 116. A method may alsoinclude receiving a tool area selection 762, 764 for the tool issue withrespect to the tool image 746. A method may additionally includeproviding access to data 114 such as tool information (e.g., a toolissue history) from the tool database 116 in response to the tool areaselection 762, 764.

It should be understood, of course, that the foregoing relates toexemplary embodiments of the disclosure and that modifications may bemade without departing from the spirit and scope of the disclosure asset forth in the following claims. By way of example, modificationsconsidered include setting up for maintenance intervals creating alarmsto wireless devices announcing time for tool maintenance, changes, ortear down reviews. It should also be understood that ranges of valuesset forth inherently include those values, as well as all incrementsbetween.

What is claimed is:
 1. A tooling system comprising: a tool scannerconfigured to scan a tool identifier on a tool; a tool database havingtool information associated with the tool identifier; and a userinterface device in communication with the tool scanner and the tooldatabase, wherein the user interface device: receives tool informationfrom the tool database in response to the scan by the tool scanner,concurrently displays a tool issue description, a tool issue image fromthe tool information of the tool database, and a plurality of sectionson the tool issue image, the plurality of sections including first andsecond sections on a cavity side of a mold and third and fourth sectionson a core side of the mold, receives a tool area selection with respectto at least one of the plurality of sections on the tool issue image,and provides access to a tool issue history from the tool database inresponse to the tool area selection of the at least one of the pluralityof sections, wherein the tool information includes tool set-upinformation, design information, maintenance instructions, toolcondition, manufacture date, warranty information, and authenticityinformation from the tool information of the tool database.
 2. Thesystem of claim 1, wherein the user interface device furtherconcurrently displays boxes, windows, areas, or buttons associated withthe tool set-up information, design information, maintenanceinstructions, tool condition, manufacture date, warranty information,and authenticity information from the tool information of the tooldatabase.
 3. The system of claim 1, wherein the user interface devicefurther concurrently displays a tool location from at least one of aglobal positioning system (GPS) and cellular triangulation.
 4. Thesystem of claim 1, wherein the user interface device further sends toolinformation to a predetermined list of contacts associated with thetool.
 5. The system of claim 1, wherein the tool identifier is at leastone of a bar code, a quick response (QR) code, a universal product code(UPC), and a radiofrequency identification (RFID).
 6. The system ofclaim 1, wherein the tool scanner includes at least one of a codescanner, a cellular phone, or an optical machine.
 7. The system of claim1, wherein the tool database includes a cloud database.
 8. A method ofusing a tooling system comprising: providing a tool scanner configuredto scan a tool identifier on a tool, a tool database having toolinformation associated with the tool identifier, and a user interfacedevice in communication with the tool scanner and the tool database;receiving tool information from the tool database in response to thescan by the tool scanner, concurrently displaying a tool issuedescription, a tool issue image from the tool information of the tooldatabase, and a plurality of sections on the tool issue image, theplurality of sections including first and second sections on a cavityside of a mold and third and fourth sections on a core side of the mold,receiving a tool area selection with respect to at least one of theplurality of sections on the tool issue image, and providing access to atool issue history from the tool database in response to the tool areaselection of the at least one of the plurality of sections, wherein thetool information includes tool set-up information, design information,maintenance instructions, tool condition, manufacture date, warrantyinformation, and authenticity information from the tool information ofthe tool database.
 9. The method of claim 8, wherein the user interfacedevice further concurrently displays boxes, windows, areas, or buttonsassociated with the tool set-up information, design information,maintenance instructions, tool condition, manufacture date, warrantyinformation, and authenticity information from the tool information ofthe tool database.
 10. The method of claim 8, further concurrentlydisplaying a tool location from at least one of a global positioningsystem (GPS) and cellular triangulation.
 11. The method of claim 8,further comprising sending tool information to a predetermined list ofcontacts associated with the tool.
 12. The method of claim 8, whereinthe tool identifier is at least one of a bar code, a quick response (QR)code, a universal product code (UPC), and a radiofrequencyidentification (RFID).
 13. The method of claim 8, wherein the toolscanner includes at least one of a code scanner, a cellular phone, or anoptical machine.
 14. The method of claim 8, wherein the tool databaseincludes a cloud database.
 15. A tooling system providing operationscomprising: provide a tool scanner configured to scan a tool identifieron a tool, a tool database having tool information associated with thetool identifier, and a user interface device in communication with thetool scanner and the tool database; receive tool information from thetool database in response to the scan by the tool scanner, concurrentlydisplay a tool issue description, a tool issue image from the toolinformation of the tool database, and a plurality of sections on thetool issue image, the plurality of sections including first and secondsections on a cavity side of a mold and third and fourth sections on acore side of the mold, receive a tool area selection with respect to atleast one of the plurality of sections on the tool issue image, andprovide access to a tool issue history from the tool database inresponse to the tool area selection of the at least one of the pluralityof sections, wherein the tool information includes tool set-upinformation, design information, maintenance instructions, toolcondition, manufacture date, warranty information, and authenticityinformation from the tool information of the tool database.
 16. Thesystem of claim 15, the operations further comprising concurrentlydisplay boxes, windows, areas, or buttons associated with the toolset-up information, design information, maintenance instructions, toolcondition, manufacture date, warranty information, and authenticityinformation from the tool information of the tool database.
 17. Thesystem of claim 15, the operations further comprising concurrentlydisplay a tool location from at least one of a global positioning system(GPS) and cellular triangulation.
 18. The system of claim 15, theoperations further comprising sending tool information to apredetermined list of contacts associated with the tool.
 19. The systemof claim 15, wherein the tool identifier is at least one of a bar code,a quick response (QR) code, a universal product code (UPC), and aradiofrequency identification (RFID).
 20. The system of claim 15,wherein the tool scanner includes at least one of a code scanner, acellular phone, or an optical machine.